Update dependency com.lmax:disruptor to v4 (branch_9x) - abandoned #3574
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Log4j Core has introduced support for Disruptor 4.x in version 2.23.0 (see the Log4j 2.23.0 release notes). To make this PR build successfully, you’ll need to merge #3562 first. |
solrbot
changed the title
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.4.4->4.0.0Release Notes
LMAX-Exchange/disruptor (com.lmax:disruptor)
v4.0.0Compare Source
WorkerPoolandWorkProcessorhave been removed, no moreDisruptor::handleEventsWithWorkerPoolDisruptorconstructors usingExecutorhave been removed. UseThreadFactoryinstead.EventHandler:BatchStartAwareLifecycleAwareSequenceReportingEventHandlerFatalExceptionHandlerandIgnoreExceptionHandlernow use the JDK 9 Platform Logging API, i.e.System.LoggerBatchEventProcessorBatchEventProcessorEventHandler::onBatchStartnow gets both thebatchSizeas well asqueueDepth(previously it hadbatchSizewhich reported queue depth)EventPollerUtil::log2throws if passed a non-positive argumentThreadHints.onSpinWait()Disruptor.handleExceptionsWith()- this had been javadoc deprecated since 2015 but not in the codeRingbuffer.resetTo()ConsumerRepository.getLastSequenceInChain()Configuration
📅 Schedule: Branch creation - Every minute ( * * * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot